Skip to content

Conversation

@atauln
Copy link

@atauln atauln commented Oct 21, 2025

This PR adds an error logging tab with automatically tracked errors in the backend. This only tracks errors on the backend (i.e. API route failures, database issues, etc.).

Copy link
Member

@andymeneely andymeneely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sure you remove the change to package-lock.json

Copy link

@llf5185 llf5185 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally consider adding .read table_sql/error_log.sql to the file create_all_tables.sql for the sake of testing.

marginLeft: "10px",
background: "none",
border: "none",
color: "#2185d0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This color gets reused, consider adding it to css/base/variables.css instead of hardcoding it.

),
},
{
menuItem: {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The errors tab shouldn't be visible to users without administrative privileges.

</span>
)}
{log.stack_trace && (
<button
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider importing buttons from semantic so that stylization is consistent with buttons elsewhere in the website.

@atauln atauln added this to the 1.9 milestone Dec 12, 2025
@atauln atauln requested review from Marrufof and Rtyujklop December 12, 2025 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Needs Planning

Development

Successfully merging this pull request may close these issues.

4 participants